Welcome to our new blog! The paint is still wet and there may be construction dust in odd places so if you find some let me know. We will discuss in the coming weeks and months a little about how we built it using a combination of ServiceNow infrastructure and the Hugo static site generator. Some functionality does not yet exist, such as commenting and liking that existed on the previous Community-site-hosted blog.
In New for Developers in Kingston - Flow Designer, Action Designer, IntegrationHub, I touched on the basics of Flow Designer.
In this post, I’ll spend some time exploring Flow Designer in more detail. Instead of trying to look at every aspect of Flow Designer in one post (that’d be a long post), I’m going to walk you through the process of creating a simple flow and we’ll touch on many of the core concepts in the process.
It is that time again in the ServiceNow year, new release Early Access season! The Kingston release has just become available to the Personal Developer Instances. If you are eagerly awaiting the new features, you can now upgrade and take them for a test drive.
In another post, josh.nerius covered one of the primary features of interest to developers in this release: Flow Designer and IntegrationHub. I am going to provide a survey of some of the other topics.
We promised we would share the results of the August, 2017 Developer Survey with you and here they are. The insights you have given us are key to the continued success of the Developer Program in providing you with the tools you need to advance your knowledge and help you to achieve your career goals. Your input is helping us to shape the future of this program.
Here is an infographic illustrating the results of the developer survey.
I’m always excited about every ServiceNow release, but Kingston brings some game changing stuff. This post is a high level overview of three new Kingston features that aren’t just ridiculously cool, they may just change the way you think about development in ServiceNow: Flow Designer, Action Designer and IntegrationHub. Note: for a deeper dive into Flow Designer, see Getting Started with Flow Designer .
That intro sounds like click-bait, but I don’t think I’m exaggerating.
It’s time for Kingston! As always, developers can participate in Early Access and can start requesting Kingston instances from the Developer Portal as of now.
To get your hands on a Kingston instance, you have a few options:
If you already have an instance You can upgrade it. From the Developer Portal, click Manage > Instance in the navigation bar. From there, click the Action dropdown and click Upgrade to Kingston.
Have you ever run into unexpected behavior when making inbound REST calls to your ServiceNow instance? Perhaps the result of a GET doesn’t contain all of the records you expect it to, or nothing happens when you try to modify a record.
In this post, we’ll explore some of the options available for debugging inbound REST API calls and the Business Rules / ACLs that might be impacting those calls.
After Your Pull Request is Accepted
Last week we posted information on how you can use ServiceNow projects to participate in Hacktoberfest. This involves some work server-side for the maintainer to be able to emulate the merging of GitHub pull requests. Let’s say you participated, submitted a pull request and it was accepted and merged into the main repository. Now what?
To reiterate slightly, you will have your own fork of the repository, and your ServiceNow instance is connected to your copy of the repository.
Source control integration was added as a feature to ServiceNow in the Geneva release. That increased by a wide margin the quality of development tools available to the ServiceNow developer. One could save code, easily move from instance to instance, backup personal developer instances, etc. One of the details of the implementation is that under the hood it is committing update sets. This complicates standard collaboration tools. GitHub pull requests and normal patch files assume that they are working on the text of code so when that text is really an XML payload, that presents a big challenge for diffing and merging.
ServiceNow provides a number of ways to export data from the platform. All of these methods are simple to use, but something that isn’t always obvious is how to include the Sys ID value associated with a record in the export.
Depending on how you plan to use the exported data, having the Sys ID is important. If you plan to do any kind of reconciliation or bring that data back into the platform in the future, having this value is critical.
